Meeting Pearls 1/Meeting Pearls Vol 1 (1994).iso/installed_progs/text/faqs/unixware-faq/text0001.txt

Text File | 1994-06-13 | 10.5 KB | 293 lines

A common complaint among long-time Unix users is the omission of
numerous standard Unix utilities from the Personal Edition.  While
ordinary users might not typically use these commands, shell scripts
do, and thus Univel may have - if inadvertently - introduced yet
another Unix version incompatibility into the already-too-large mix.

Among the items lacking in the Personal edition are: the C and Korn
shells (the Windowing Korn Shell [wksh] _is_ included, however),
banner, calendar, head, join and dc.  These commands _are_ available,
however, in the Advanced Utilities module (an add-on optional
package).

Oh, and of course TCP/IP has been left out of the release 1.0 Personal
Edition, too, but will be bundled with 1.1.  (NFS, however, is NOT
bundled.)

Subject: S4) Does UnixWare come with TCP/IP and/or NFS?

The Release 1.0 Personal Edition does not include TCP/IP or NFS in the
basic system.  A TCP/IP+NFS package is available from Univel; a
similar offer, plus a TCP/IP-only option, is available from
Information Foundation.

Release 1.1 _will_ include TCP/IP in the Personal Edition, but _not_
NFS.  NFS remains an extra-cost option.

TCP/IP and NFS are bundled with the UnixWare Application Server in
both release 1.0 and 1.1.

Subject: S5) Will UnixWare 1.1 have TCP/IP bundled with the Personal Edition?

Yes.

Subject: S6) Can I replace the stock UnixWare X server with something faster?

Yes.  Several vendors sell X servers which can be used to speed up X
on your UnixWare system.  Typically, these vendors will also sell you
drivers for specific cards as well.  A partial list of such vendors
follows:

  Quarterdeck Office Systems' Hyper-X
  (formerly sold as Pittsburgh Power Computing's Hyper-X)
  150 Pico Boulevard
  Santa Monica, CA 90405
  [phone]
  [phone] FAX
  [e-mail]
  [e-mail]
  Call 800-354-3222 Extension 8G8 for special introductory offer
  Hyper-X should also be available through conventional distribution
  channels, eg dealers selling other Quarterdeck products (QEMM, Desqview)

  Metrolink Metro-X
  2213 W. McNab Road
  Pompano Beach, FL 33069
  [phone]
  [phone] FAX
  [e-mail]

  Snitily Graphics Consulting Service (renamed/acquired-by X/Inside?)
  894 Brookgrove Lane
  Cupertino, CA 95014
  [phone]
  [phone]
  [phone]
  [e-mail] or ...!mips!zok!info

There is also XFree86.  From David Wexelblat's 31 Oct 1993
announcement of the release of XFree86 2.0:

  XFree86 is a port of X11R5 that supports several versions of Intel-based
  Unix and Unix-like operating systems.  The XFree86 servers are derived
  from X386 1.2, which was the X server distributed with X11R5.  This
  release consists of many new features and performance improvements as well
  as many bug fixes.  The release is available as source patches against the
  MIT X11R5 code, as well as binary distributions for many architectures.

  Source patches based on X11R5 PL25, from MIT, and as an upgrade from
  XFree86 1.3 are available via anonymous FTP from:

       ftp.x.org (under /contrib/XFree86)
       ftp.physics.su.oz.au (under /XFree86)
       ftp.win.tue.nl (under /pub/XFree86)
       ftp.prz.tu-berlin.de (under /pub/pc/src/XFree86)

    Binaries are available via anonymous FTP from:
                ftp.physics.su.oz.au            - SVR4 binaries
                        under /XFree86/SVR4
                ftp.win.tue.nl                  - SVR4 binaries
                        under /pub/XFree86/SVR4
                ftp.tcp.com                     - SVR4 binaries
                        under /pub/SVR4/XFree86
                stasi.bradley.edu               - SVR4 binaries
                        under /pub/XFree86/SVR4

  The next release of the Prime Time Freeware CD-ROM will include XFree86 2.0
  in pkgadd format.  Contact:

    Prime Time Freeware
    370 Altair Way, #150
    Sunnyvale, CA 94086
    [phone] Voice
    [phone] FAX
    [e-mail]

If you have access to Usenet news, see the newsgroup
comp.windows.x.i386unix for ongoing discussions of XFree86 and other
Intel/Unix/X solutions.

Subject: S7) Why can't I access the CD-ROM drive after I've just installed from it?

Bill Rosenblatt writes:

This is a known bug that is supposed to be corrected for release 1.1.
There's a relatively simple workaround:

   1. Shut down your machine.
   2. Open the machine and remove the SCSI adapter card.
   3. Leave the cover off and reboot.  The system will print an error
      message, but it will come up.
   4. Shut down again.
   5. Replace the SCSI card and put the cover back on the machine.
   6. Reboot again.  The system will rebuild the kernel, which will
      take a few minutes.  Then it will tell you to reboot.  Do so.
   7. When the system comes up again, the CD-ROM should be accessible.

Another method I received from UnixWare tech support proceeds as follows:

  When the CD-ROM driver seemingly drops out of sight in UnixWare, one
  cannot read from a CD, nor can one mount a cdfs file system.

  To correct this, first determine the proper name of your CD-ROM device
  driver. Change directory to /dev/cdrom and do an ls. There will be a
  driver file there in the form "cxtxlx" where the x's are SCSI controller
  number, tag numberm and logical unit number respectively. (e.g. the driver
  will be something like "c0t4l0" or c0t3l1") Write this name down!

  Next, it is necessary to create a "raw device." Change directory to /dev
  and "mkdir rcdrom" to create a directory called /dev/rcdrom. Then change
  to this new directory and make nodes for a CD based on the name found in
  /dev/cdrom.

                 mknod c0t4l0 c 0 0
                 mknod cdrom1 c 0 0

  These commands in succession are "make node <device driver> see-zero-zero"
  and "make node cdrom1 see-zero-zero." Note that the next-to-last character
  in the device driver name is an "ell" not a "one."

  While still in the /dev/rcdrom directory, make the whole directory
  readable, writable, and executable to everyone.

                 chmod 0777 .
                 chmod 0777 *

  and everything should be fine. You can check by clicking on the
  "Disks Etc." icon to see if the CD-ROM icon is there.


Subject: S8) Why does my data comm package lose characters constantly at high speeds?

Bill Rosenblatt again:

   The odds are good that the problem is with the UART on your
   serial interface card.  If you have a relatively low-end PC,
   you probably have an old-style UART that interrupts the CPU after
   it receives every character.  Unix usually handles serial interrupts
   at a low level (lower than DOS does, for example), so it can't keep
   up if the speed is too high, usually above 9600bps.

   To fix this, you need to get a new UART, a 16550 UART that has
   a 16-byte buffer.  The 16540 UART, with a 2-byte buffer, may also
   be enough of an improvement.  If your UART isn't in a socket,
   then you will have to replace the entire card.  Luckily, these
   are not very expensive--about $40 for a single-port card or
   $70 for a standard PC multi-port card.

   Additionally, you need a device driver
   that knows how to take advantage of the UART's buffering.
   UnixWare has such a device driver (asyhp), but the current version is
   known to be flaky.  Novell should have a fix for this available on
   ftp.novell.com before 1.1 comes out.  In any case, here's
   what you need to do to enable the driver, courtesy of Joao Costa
   ([e-mail]):

   Just go to /etc/conf/sdevice.d, edit asyhp and turn N to Y for
   the ports you want, then edit asyc and turn Y to N on those ports.
   Rebuild the kernel and, when the new kernel boots, you'll have a status
   message about your 16550 ports.

Subject: S9) How can I make or get an emergency boot floppy?

Rick Richardson of DigiBoard ([e-mail]) spells out what the EBF is:

    What is it?
    An emergency boot floppy (EBF) allows you to boot UnixWare off
    a floppy disk, with a minimal set of commands available to you.
    If possible, the EBF will mount the hard disk partition and let
    you recover any data that may be on the partition, or fix important
    files (such as /etc/passwd) that you might have lost or corrupted.
    An EBF avoids the tedious procedure of having to reload Unix in
    these cases.

    Every System Administrator should have an EBF in their possession.

An "anonymous" poster from Novell recently broke the good news that
many have been waiting for:

  ...you can now generate your own Emergency Boot
  Floppy (ebf) for UnixWare 1.0.  There is an ebf update available
  on ftp.novell.com (and on CompuServe).  The file is ebf.tar and is
  located in /pub/unixware/Updates.  This package DOES NOT create an ebf, but
  installs a utility to do so.

  Get ebf.tar, and as usual untar it.  chmod the .run file to be
  executable and then execute it to install the package.

  Once the package is installed, execute the command
  /usr/sbin/emergency_disk diskette1 (or diskette2).  This ought to
  do it.

Subject: S10) How do I set a dialup password on UnixWare for a specific port?

Andrew Josey of Unix Systems Labs Europe ([e-mail]) provides
the following guide:

  Two files must be created in the /etc directory, and for ease of
  use you can add a user (say called dialup).

  (1) /etc/d_passwd
  ------------------

  This is the dialup password file.

  # ls -l /etc/d_passwd
  -rw-------   1 root     root          70 May 13 07:44 /etc/d_passwd
  #

  This contains entries for login shells (uucico,ksh and sh).
  Usually there is no additional password for uucico.
  Interactive logins (ksh, and sh) have passwords.

  The encrypted password must be put in the file, note spaces and position
  of the colon delimiters are critical.

  # cat /etc/d_passwd
  /usr/lib/uucp/uucico::
  /usr/bin/ksh:66NOJGfJw4I.A:
  /usr/bin/sh:66NOJGfJw4I.A:
  #

  (2) /etc/dialups
  -----------------
  The second file /etc/dialups dictates which devices are
  to have the dialup password prompt

  # cat /etc/dialups
  /dev/tty00
  /dev/tty01h


  (3) Setting the password
  ------------------------
  To set the password, I have a login entry for a user dialup (this
  just executes date as the login shell).

  Thus on the day to change the password

    i)

    # passwd dialup
    New password:
    Re-enter new password:
    #

    ii)

    # grep dialup /etc/shadow|cut -f2 -d":" >>/etc/d_passwd

    This appends the new dialup onto the end of the d_passwd file.

    iii)

    Edit the file with vi to place the new encrypted password
    in the appropriate fields marked XXXX below:

    /usr/lib/uucp/uucico::
    /usr/bin/ksh:XXXX:
    /usr/bin/sh:XXXX:

Subject: S11) How do I configure electronic mail on UnixWare?